docs(matrix-communication): say how to read a room log - #107
Merged
Conversation
The log is an event stream. Adjacent lines from one sender are adjacent events, and a reaction or redaction line names its target only when the daemon still holds that message; otherwise the honest report is that the log does not record which one. Written from the failure that produced #104: two reactions and two redactions within three seconds were summarised as someone taking back what they had just set. They were two different messages. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
github-actions
Bot
added
documentation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
A bare '#104' does not autolink in a repository file — only in comments and issue bodies. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Merged
CybotTM
added a commit
that referenced
this pull request
Aug 13, 2026
Minor release. Delta since v3.0.0: room-log reading rules — adjacency and redaction-target semantics (#107).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #104, which fixed the data. This writes down the reading rule that the missing data exposed.
#104 was found because a summary got it wrong: two reactions and two redactions from one sender within three seconds were reported as "took back the reactions just set". They were two different messages. The log carried no relation at all, so there was nothing to check against — but the failure was not only the missing field. It was treating adjacency as a relation and reporting the result as observation.
SKILL.mdgains a "Reading a room log" section: the log is an event stream, consecutive lines from one sender are consecutive events, and a reaction or redaction line names its target only when the daemon still holds that message. When it does not, the line says only that it happened, and that is what to pass on.AGENTS.mdgets the one-line index entry.The corresponding data-side rule shipped in v3.0.0 and is not repeated here.